OpenEdge Data Management:<br />Database Administration Enabling auditing

Auditing is enabled in an OpenEdge database with the PROUTIL utility. The first time that auditing is enabled for a new 10.1A database, the auditing meta-schema tables for audit policies, events, and data are created for the database. See the "Auditing tables" section for descriptions of the tables and indexes. Enabling a database that is not new in 10.1A also adds additional meta-schema tables that are included in 10.1A by default.

When enabling a database for auditing, you must specify an area for the audit tables. Do not place the auditing tables in the schema area. It is best to create a new area exclusively for auditing. You can also specify an area for the audit table indexes. If you anticipate generating large volumes of audit data, you may achieve better performance by separating the data and indexes. You can also choose to deactivate the non-unique auditing indexes. This could provide you with a performance boost. Deactivated indexes can be activated at a later time using PROUTIL IDXBUILD.

Create a structure file (.st) defining an area for your audit tables, and optionally an area for your audit indexes.

Add the areas to your database using PROSTRCT ADD. For more information on creating a structure file, and using PROSTRCT, see Chapter 14, " Maintaining Database Structure."

Enable your database with PROUTIL ENABLEAUDITING. The following command enables auditing for a database named sample-db, and places the auditing tables in an area named “Audit Area”, the auditing indexes in an area named “Audit Indexes”, and deactivates the non-primary indexes:


proutil sample-db -C enableauditing area “Audit Area” - indexarea “Audit Indexes” deactivateidx

Once you have enabled a database for auditing, you must define and activate an auditing policy to begin generating an audit trail. For information on auditing policies, see the Audit Policy Maintenance online Help.